UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

WebSphere MQ started tasks are not defined in accordance with the proper security requirements.


Overview

Finding ID Version Rule ID IA Controls Severity
V-3904 ZWMQ0030 SV-7526r2_rule DCCS-1 DCCS-2 Medium
Description
Started tasks are used to execute WebSphere MQ queue manager services. Improperly defined WebSphere MQ started tasks may result in inappropriate access to application resources and the loss of accountability. This exposure could compromise the availability of some system services and application data.
STIG Date
z/OS RACF STIG 2019-09-27

Details

Check Text ( C-4628r1_chk )
a) Refer to the following reports produced by the RACF Data Collection:

- DSMON.RPT(RACSPT)
- RACFCMDS.RPT(LISTUSER)

Provide a list of all WebSphere MQ Subsystem Ids (Queue managers) and Release levels.

b) Review WebSphere MQ started tasks and ensure the following items are in effect:

NOTE: ssid is the queue manager name (a.k.a., subsystem identifier).
ssidMSTR is the name of a queue manager STC.
ssidCHIN is the name of a distributed queuing (a.k.a., channel initiator) STC.

1) Each ssidMSTR and ssidCHIN started task is associated with a unique userid.
2) All ssidMSTR and ssidCHIN started tasks are defined to the STARTED resource class.
3) All ssidMSTR and ssidCHIN started tasks userid are defined as a PROTECTED.

c) If both of the items in (b) are true, there is NO FINDING.

d) If either item in (b) is untrue, this is a FINDING.
Fix Text (F-18797r1_fix)
Each queue manager started task procedure xxxxMSTR and distributed queuing started task procedure xxxxCHIN will have a matching profile defined to the STARTED resource class. Create a corresponding userid for each started task. The STC userids will be defined as PROTECTED userids. Queue manager and channel initiator started tasks will not be defined with the TRUSTED attribute.

The following sample contains commands to properly define the required Started Procs:

Note that this example uses "qmq1" as the value for ssid.

AU qmq1mstr NAME('STC, MQSERIES') NOPASS DFLTGRP(STC) OWNER(STC) DATA('MQSERIES QUEUE MANAGER PROC')

AU qmq1chin NAME('STC, MQSERIES') NOPASSDFLTGRP(STC) OWNER(STC) DATA('MQSERIES DISTRIBUTED QUEUING CHANNEL INIT PROC')

RDEF STARTED qmq1mstr.** UACC(NONE) OWNER(ADMIN) AUDIT(ALL(READ)) DATA('MAP qmq1mstr PROC TO qmq1mstr USERID') STDATA(USER(=MEMBER) GROUP(STC) TRACE(YES))

RDEF STARTED qmq1chin.** UACC(NONE) OWNER(ADMIN) AUDIT(ALL(READ)) DATA('MAP qmq1mstr PROC TO qmq1chin USERID') STDATA(USER(=MEMBER) GROUP(STC) TRACE(YES))

SETR RACL(STARTED) REFRESH